Why msg is always set to null when instantiate2 while Wasmd v0.31.x include msgs when creating address?

See https://medium.com/cosmwasm/dev-note-3-limitations-of-instantiate2-and-how-to-deal-with-them-a3f946874230

I added #1398 for future readers

I got it.
However, according to the link you provided, it seems that fix_msg should be null, not that instantiate msg should be null and current code is making instantiate msg to null.

It refers to different aspects of the same thing. If msg is null or empty during address generation, fixed_msg must be false in the actual instantiation.

If msg is null/empty (during address generation) and fixed_msg = false, then you can instantiate the contract with any msg you want without affecting the generated address.

To be honest, I am not familiar with wasmd, so I'm not sure how to use instantiate2.
If you have a chance, could you make a test code that compares the address obtained with instantiate2Address and the address of the contract instantiated with instantiate2 in the script/wasmd chain?

And thank you for your kind answers :)

Yeah, it's still early for instantiate2 and not much resources are out there. Feel free to subscribe to #1399 to see

• Pre-calculation
• Actual instantiation

in CosmJS. The tests for this ticket will make a few things clearer I guess.

A Pre-calculation tool here
https://blueprints.juno.giansalex.dev/#/contract/tools

Oh, nice! I strongly advise for removing the msg input field there. Nobody should need to use it.